cc @ruflin @webmat @kaiyan-sheng

I see a few renames, this makes this a breaking change, isn't it?

afaik this is not a breaking change for now

• 2 fields have been added at EC2 metadata
• renames have only been introduced at docs to sync with code

sorry you are right! change LGTM, it seems it needs a mage fmt

thanks for the reviews

I was silently expecting some comments regarding this file:
https://github.com/elastic/beats/blob/master/libbeat/processors/add_cloud_metadata/_meta/fields.yml

@ruflin I guess that yaml sounds like global to all cloud metadata, and shouldn't be touched until we bring those 2 fields to all other cloud providers. If I'm wrong, pls, correct me

You can definitely add them there, I see cloud.project.id is in (GCP only?). If/Once these new fields make it to ECS you can import ECS and remove them from this fields.yml

@odacremolbap you didn't add the fields, something is wrong here?

@exekias I'll open a new issue to gather that info (image, account) from other providers, then once they are available for all (or most) add it

why not adding them now? that would mean master is missing these fields, while they may be reported in some cases. It sounds like having fields.yml in is a safer play, you can always change them when adding new providers